|
|
|   |
|
|
|
HP ProLiant NC1020 Gigabit Server NIC Driver for Red Hat Enterprise Linux 3
 version
7.2.24e
 
(23 Apr 2004)
|
|
|
Click the link below to download this software:
|
|
|
|
bcm5700-7.2.24e-1.src.rpm
|
|
|
HP ProLiant NC1020 Gigabit Server NIC Driver for Red Hat Enterprise Linux 3
|
|
|
|
|
|
|
|
|
|
|
|
  Installation
|
┬╗
top of page
|
|
|
1.This package requires the kernel source code as well as setting up the source tree. Verify the source code /usr/src/linux- directory exists.
# cd /usr/src/linux-
If the kernel source code is not present, then refer to the "Kernel Source Code Setup" section.
2.Install the source RPM package.
# rpm -ivh bcm5700-.src.rpm
3.Build the binary RPM for the bcm5700 driver.
Red Hat Installation:
# cd /usr/src/redhat
# rpmbuild -bb SPECS/bcm5700.spec
SuSE SLES9 Installations:
# cd /usr/src/packages
# rpmbuild -bb SPECS/bcm5700.spec
If you get an error during the build process, refer to the "Kernel Source Code Setup" section to correctly setup the source tree.
4.Check for the existence of a current version of the bcm5700 package as follows:
# rpm -q bcm5700
If an old version of the package exists, the RPM package should be removed.
# rpm -e bcm5700
Then remove the loaded bcm5700 module.
# rmmod bcm5700
Verify that the old bcm5700 package has been removed as follows:
# rpm -q bcm5700
5.Install the new RPM package. This installs the bcm5700 driver and man page. Do not use the U (Upgrade) flag in the RPM command below - previous bcm5700 drivers must be removed as described in step 4 above before installing this version.
# rpm -ivh RPMS/i386/bcm5700-.i386.rpm --force
The bcm5700.o module is installed in the following directory:
Red Hat EL 3
/lib/modules//kernel/drivers/net
SuSE SLES9
/lib/modules//kernel/drivers/net/bcm
For SLES9 bcm5700.ko module will be installed instead of bcm5700.o.
6.Configure your network setting and address. You may need to refer to your Linux vendor documentation. Use the "netconfig" tool for Red Hat configuration.
For SLES9, user has to specify the module as bcm5700 while configuring the network. The module can be specified in Hardware Details of Advanced configuration.
7.Ensure that the /etc/modules.conf file is configured similar to the example listed below. The example below is presented as if more than one adapter is present. If so, one eth# instance should exist for each ethernet port. Refer to the modules.conf man page for more information.
alias eth0 bcm5700
alias eth1 bcm5700
alias eth# bcm5700
For SLES9, the configuration file is /etc/modprobe.conf or /etc/modprobe.conf.local.
8.You can now reboot your server. Upon reboot the network should start with the bcm5700 driver loaded and the correct network configuration. To verify that the bcm5700 driver is loaded, use the following command.
# lsmod
If bcm5700 is listed then the bcm5700 driver loaded.
Note: By default SLES9 installs the tg3 driver. If the tg3 driver is installed, unload the tg3 driver first.
Use ifconfig to bring down all eth# interfaces used by tg3.
# ifconfig eth# down
Now remove or unload the tg3 driver.
# rmmod tg3
You may also need to manually edit the /etc/modules.conf file to change the driver from tg3 to bcm5700.
For SLES9, the configuration file is /etc/modprobe.conf or /etc/modprobe.conf.local.
alias eth0 tg3
and replace tg3 with bcm5700:
alias eth0 bcm5700
Note: If the above entry doesn't exist add it in configuration file. Load the bcm5700 driver:
# insmod bcm5700
or
# modprobe bcm5700
Note: It is preferred to use modprobe in SLES9. insmod may not work the way it worked in 2.4 kernels.
Use ifconfig to bring up the network with the new driver:
# ifconfig eth# up
Refer to the man pages for lsmod, ifconfig, rmmod, insmod, modprobe, modules.conf and modprobe.conf for more detailed information.
|
|
|
  Revision history
|
┬╗
top of page
|
|
|
Version 7.2.24e
Initial revision
|
|
|
|
|
|
|
